feat: Risk upgrade path integration test - #400

Issue

Fixes #76

Solution

To avoid having one upgrade test per TLS configuration (x4), we deploy the products in full TLS configuration since this gives us the most coverage when upgrading.

Checklist

• I have added or updated relevant documentation.
• PR title makes an appropriate release note and follows conventional commits syntax.
• Merge target is the correct branch, and relevant tandem backport PRs opened.
• Add this feature for COS
• Remove these tests for track/2 since we do not have the juju_charm feature there (not refreshing to latest revision in updated track/risk), and feature this for track/3.0 once released:
  • feat: COS and COS Lite 3.0 #381

Context

Testing Instructions

just integration cos_lite/risk_upgrades
See these CI runs for:

• COS Lite
• COS

Upgrade Notes